@Konippi Thank you for the contribution! Our logging story definitely needs more user visibility, and having it under a /logdump command makes sense to me - we could add extra help comments about how to e.g. set the logging env var even (doesn't need to happen in this PR, just get the functionality working).

I would prefer it changed though to instead just copy qchat.log and mcp.log.

My reasoning:
Logs under qlog includes everything unrelated to the actual qchat binary as well, e.g. the desktop app and qterm. Any slash command within chat should probably instead restrict itself to qchat.log and (maybe with a --mcp argument) mcp.log.

If a user is running /logdump within q chat, it's just a bit strange to couple it with everything else in that directory unrelated to q chat. I would expect something like q logdump from the top level to have this type of behavior.

We've never had any reason to request logs for the others. Plus side, this also simplifies the initial implementation a bit

Thanks for the feedback! You're absolutely right about the scope issue.

I'll update this PR to focus on qchat.log only to keep it simple and get the core functionality working.

For mcp.log inclusion with the --mcp flag, I'll handle that in a separate PR once this base functionality is merged.